System and Method for Implementing a Universal Messaging Gateway (UMG)

ABSTRACT

The system and method for implementing a Universal Messaging Gateway (UMG) disclosed herewith provides telecommunications Network Operators (NO) and like related parties with innovative and flexible art for delivering domestic and foreign network originated Multi-media traffic and/or, more generally, interactive and/or synchronous mobile text and related telecommunications messaging or information services to a large number of related receiving telecommunications network equipment (as ESMEs and/or SMS-Cs in relation to SMS traffic).

RELATED APPLICATIONS

This is a continuation of U.S. application Ser. No. 12/765,388, filedApr. 22, 2010, which is a continuation of U.S. application Ser. No.12/242,040, filed Sep. 30, 2008, now U.S. Pat. No. 7,733,887, which is acontinuation of U.S. application Ser. No. 10/671,798, filed Sep. 29,2003, now U.S. Pat. No. 7,447,219. The contents of all of these relatedapplications are incorporated herein by reference in their entirety.

BACKGROUND ART

Interactive mobile text and related services (including Short MessageService (SMS) and Multi-Media Services (MMS)), which facilitate such artas voting, gaming, information products, and real-time messagingcontinue to evolve in their popularity and ubiquity among networkoperators and mobile subscribers alike. The services provide forinteractive and/or synchronous entertainment and commercial activities,as with real-time quiz shows, questionnaires, polls and related events.Indeed, owing to the growth, popularity and utility of suchapplications, telecommunications Network Operators (NO), marketers, andlike interested parties seeks to build upon and capitalize such successby adding more applications and reaching more subscribers.

Nonetheless the prior art has neither demonstrated nor intimated anevolution of its teachings in this regard. Indeed, consider U.S. Pat.No. 6,178,331 to Holmes, et al. entitled System and process for allowingwireless messaging, and U.S. Pat. No. 6,493,558 to Bernhart, et al.entitled TD-SMS messaging gateway which both delimit art pertaining toSMTP Gateways and like systems, and indeed, unlike the system and methodfor implementing a Universal Messaging Gateway (UMG) of present, is onlyintended to serve subscribers of the home network and thereby does notinclude capability/ities of our invention to provide gateway service toGSM foreign subscribers and like users.

At a more generic level, U.S. patent application Ser. No. 20020087704 byChesnais, et al. entitled Systems and methods for routing messages tocommunications devices over a communications network details a gatewaysystem for performing protocol conversions. The art relating to ourinvention disclosed herewith however, exceeds such teachings, by interalia, providing methods and systems for receiving Short Message Service(SMS), Multi-Media Service (MMS) and the like from foreign SMSCs, MMSCsand the like and routing them to the relevant home network and/orcontent providers.

References Cited

U.S. patent application Ser. No. 20020087704 July, 2002 Chesnais, et al.709/228

U.S. Pat. No. 6,178,331 January, 2001 Holmes, et al. 455/466

U.S. Pat. No. 6,493,558 December, 2002 Bernhart, et al. 455/466

TECHNICAL FIELD

The present invention relates generally to wireless communications andgateway services; and more specifically, to a system and method forimplementing a Universal Messaging Gateway (UMG).

SUMMARY OF THE INVENTION

In the preferred embodiment, the system and method for implementing aUniversal Messaging Gateway (UMG) disclosed herewith providestelecommunications Network Operators (NO) and like related parties withinnovative and flexible art for delivering domestic and foreign networkoriginated Multi-Media traffic and/or, more generally, interactiveand/or synchronous mobile text and related telecommunications messagingor information services to a large number of related receivingtelecommunications network equipment (as ESMEs and/or SMS-Cs in relationto SMS traffic).

In keeping with much of the background art, literature, leanings andteachings of the field, in introducing and launching interactive and/orsynchronous mobile text and related telecommunications messaging orinformation services, including in this instance for the purposes ofillustration, SMS applications, Application Service Providers (ASPs)must engage and interconnect with multiple service providers. From theASPs' perspective, integrating with mobile networks remains a costly andlabourious task, as traditional implementations have required thedeployment of transmission facilities to each Network Operator's (NO)Short Message Service Center (SMS-C) (in this instance). Furthermore,operators will typically assign dissimilar short-codes or likemechanical/logical instructions for a given application, therebycreating confusion when wireless subscribers roam between carriers andgeographic regions, and indeed dilutes the overall value of the service.

Thereby it is an aspect of the present invention to enable and provide areply path for foreign subscribers to send interactive and/orsynchronous mobile text and related telecommunications messaging orinformation services, including in this instance for the purposes ofillustration, SMS messages to a given NO's Short Message serviceproviders. In one embodiment therefore, the method, system andarchitecture addresses the need to provide a mechanism for routingmobile terminated SMS messages from the SS7 network (in this instance)to the connected ESMEs via, in this instance for the purposes ofillustration, a Short Message Peer to Peer (SMPP) protocol. In anotheraspect, in relation to the delivery of Short Messages (SM), connectionto multiple SMSCs is also articulated and provided for when routing SMPPtraffic (in this instance) from SMSCs to ESMEs.

In elucidating the art further, the invention thus provides ASPs asingle point of access to a given NO. The computer program product whichimplements the system and method for implementing a Universal MessagingGateway (UMG) redirects and terminates traffic to a virtual mobilestation address, then delivers the traffic to the appropriate ASP. Thevirtual mobile station address can be communicated to all subscribers ina given region, and can also deliver the SMS and/or other such relatedMulti-Media traffic to a subscriber irrespective of their roaming state.Any mobile subscriber world-wide has the ability to respond to anadvertisement through a universal destination number assigned for thecorresponding application.

A security and network management algorithm has been developed which, inalternate embodiments, when articulated with the system and method forimplementing a Universal Messaging Gateway (UMG) (which exists as partof a computer program product) provides mechanisms for the blocking ofunauthorized messaging, multi-media and other informational traffic fromentering a given mobile network.

Management and administrative functions for the disclosed invention maybe achieved through a single graphical user interface (GUI). Saidinterface allows for the configuration, connection, and disconnection ofSMPP and/or like protocols and/or like logical connections.Practitioners skilled in the art will recognize that the inventionremains wholly scaleable as needs and capacity requirements require.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a typical, non-limiting embodiment of the systemlevel architecture employed in the disclosure of present.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Members skilled in the art will recognize that the ensuing represents anillustrative recital of the preferred embodiments of the invention ofpresent and other embodiments may be articulated, gleaned andarticulated from such while still remaining with in its spirit andscope. Indeed, equivalents found within the state of the art, and thosewhich may reasonably and effectively be deemed equivalent in the futureshould also be understood as being incorporated by reference hereto andsuch. Furthermore, much of the language has been illustrative and is tobe construed as expressly for pedagogical purposes in helping elucidatethe art as concisely and beneficially as practical.

With reference now to FIG. 1, the system and method for implementing aUniversal Messaging Gateway (UMG) 100, which exists as part of acomputer program product can be functionally divided for the purposes ofillustration among the following elements. Receiver Managers (110A,110B), which for instance, manage and maintain External Short MessageEntity (ESME) 70 connections (110A), Short Message Service Center (SMSC)60A connections and other such connections in keeping with the state ofthe art. Specifically in relation to short message service (SMS), anSMSC Transmitter Manager 140, via the internally articulated SMS ReplyServer 130, manages and maintains SMSC (60A) connections from thecomputer program product 100 to the relevant SMSC(s) 60A. Anormalization engine 170 performs address normalizations within theinvention. A routing engine 120 allows for automatic routing of messagesdelivered over Short Message Peer-to-Peer (SMPP) protocol receiverconnections (although those skilled in the art will recognize that thereare a variety of protocols which serve similar technical and mechanicalpurposes and ends which may be employed without diluting the intent andscope of the invention of present). The Home Location Register (HLR)module 190 of the invention 100, provides HLR 40 functionality to theGSM network (internally articulated with an HLR lookup database 191).Furthermore, the Mobile Switching Center (MSC) module 180 translates(181), co-ordinates and manages the protocol connections and likelogical commands and overall MSC 50 functionality to the GSM network.Modules 180 and 190 handle much of the SMS traffic (in this instance)from foreign SMSCs 60B. Internal to the art of the computer programproduct which implements the system and method for implementing aUniversal Messaging Gateway (UMG) 100, remains common, generic loggingand network management elements 150, which are responsible for systemlogs, event records (ED), Simple Network Management Protocol (SNMP)based network management (of course, practitioners skilled in the artwill recognize that other protocols may be employed and managedaccordingly without necessarily diluting the scope and intent herewith).Residual elements of the invention 100, include a web-based or othersuitably articulated provisioning interface 100B and a generic,multi-faceted interface for receiving protocols, connections and otherlike logical commands from various other networks and/or networkelements as the art evolves 100A.

Continuing with reference to FIG. 1, the invention's 100 SMSC ReceiverManager 110B is responsible for SMPP receiver bind connections to therelevant SMSC(s) (60A, 60B) and the invention's articulated MSC Module180 (for foreign SMSC(s)). SMSC Receiver connections connect from theinvention to receive messages from an operator's SMSC(s) (60A, 60B). Thecomputer program product which implements the system and method forimplementing a Universal Messaging Gateway (UMG) 100 manages andcontrols SMSC connections, providing connection management services andconsolidates SMPP data flows. Practitioners skilled in the art willrecognize that exist a variety of protocols which serve similartechnical and mechanical purposes and ends which may be employed withoutdiluting the intent and scope of the invention of present. Likewise,members skilled in the art will recognize that the instruction providedherewith need not be limited to Short Messages (SM) and their relatedtechnologies and the limitations of the description serve only for thepurposes of illustration and simplicity of purpose.

In elucidating the art relating to the SMSC Receiver Manager 110Bfurther, consider that in the preferred embodiment, an SMPP Receiverlink to a SMSC must be established before messages can be received fromit. Also in the preferred embodiment, the computer program product whichimplements the invention establishes all SMPP connections to SMSC(s)upon startup. (In alternate embodiment, the art may also be manipulatedas to disable this auto connection feature). The SMSC Receiver Managersupports connections to multiple SMSCs. Where multiple connections tothe same SMSC account need to be established, the art and logic has beenarticulated such that multiple SMSC profiles with the same loginparameters can be created. Once the said connection is established, theSMSC Receiver Manager Module will accept all incoming deliver=messagesfrom the SMSC. In the preferred embodiment, all other SMPP PDUoperations (except Enquire Links) will be rejected.

In alternate embodiments, the computer program product which implementsthe system and method for implementing a Universal Messaging Gateway(UMG) can maintain and ensure the status of a SMPP receiver connectionby sending enquire link messages to the connected SMSC. The connectedSMSC is to respond with a enquire link response message, indicating theconnection is available. Incoming enquire links will be answered with anenquire link response message. Where the connected SMSC does not respondto a enquire link message, the art of the invention has been articulateto send an unbind message to the connected SMSC, and the connection isterminated.

In advancing the connection management functionality of the invention,the invention throttles incoming SMPP receiver links in order to preventthe excessive utilization of network elements by external entities. Inan SMSC Receiver bind, only the numbers of messages defined by thethrottling parameter (e.g. messages/second or other such configurabletimeframe) configured in the SMSC Receiver profile are allowed.Subsequent messages are rejected with a configurable error code.

Continuing with reference to FIG. 1, the invention's 100 normalizationand filter engine(s) 170 provide for flexible address normalization andblocking capabilities. One of the unique features of the inventiondelimits art which enables the network operator (or like) to blockincoming traffic based on the service centre that the message was sentfrom. (Although in light of the state of the art, this feature does notapply to messages received from the SMSCs over the SMPP connections). Inalternate embodiments, the invention may also enable the networkoperator to block incoming traffic based on the origination address ofthe message. Prefix matching on the origination address is supported.Messages that are originated from the blacklisted originators arerejected. If the message is blocked, the computer program product whichimplements the system and method for implementing a Universal MessagingGateway (UMG) 100 returns a configurable error code.

Now, the Routing Engine 120 of the invention allows thetelecommunications carrier (or like entity) to define flexible messagerouting for forwarding messages to ESME(s). In view of the importance ofthe art, the following considerations remain instrumental (though merelyillustrative and non-limiting as practitioners skilled in the art willrecognize) when defining the relevant logic as they pertain to saidrouting rules:

1. Rules are considered in priority order. Priority is not necessarilyunique; in alternate embodiment, time of creation may be used as atiebreaker value. In alternate embodiment, higher priority will be givento the older rule when there are multiple rules having the samepriority.

2. In the preferred embodiment, the first rule that matches will be usedand all other rules will be ignored. (In alternate embodiments,variations on this theme may be enjoyed and practised).

3. Where no rules match, the message will be rejected; with configurableerror code.

4. Once the Destination ESME ill is identified, the message will berouted to the Destination ESME. If the ESME has established multipleconnections with more than one node under a cluster configuration, themessage will be routed via the closest connection (i.e. on the samenode, if connection exists). When more than one ESME connections isestablished on a node, messages will be delivered to ESME usinground-robin.

Furthermore, non-limiting, illustrative examples of routing parameterssupported by the computer program product which implements the invention(and therefore, by implication, the routing rules), include, incomingSMSC Connection ID, termination TONfNPI/MSISDN, originationTONfNPI/MSISDN, protocol ill, data coding scheme, and SMSC Address.

Still with reference to FIG. 1, the inventions' 100 ESME ReceiverManager IIOA is responsible for handling SMPP receiver bind connectionsfrom the ESME(s) 70. ESME 70 initiate SMPP receiver bind to connect tothe invention 100 to receive messages. The computer program product 100manages and controls ESME connections, providing connection managementservices and consolidates SMPP data flows. Practitioners skilled in theart will recognize that other protocols may be employed and managedaccordingly without necessarily diluting the scope and intent herewith.

Said ESME Receiver Manager 110A provides overall connection managementfunctionality including, authentication, connection monitoring andmessage buffering.

In order to receive messages, the ESME partner 70 must first establish areceiver bind connection to the invention 100. Each ESME partner 70 thatconnects to said invention 100 must be provisioned with a respectiveESME Receiver profile, The invention 100 authenticates each ESME bindreceiver request. For the purposes of illustration, in maintaining thesecurity and integrating of communications, the following parameters areordinarily verified, in the preferred embodiment, before accepting thebind request:

1. System Type, System ID, Interface Version, and Password supplied inthe bind receiver request all must match a provisioned ESME ReceiverProfile;

2. ESME Receiver Profile must be in a Enabled state;

3. The number of bound in ESME Receivers must be less than theconfigured “Maximum Number of Connections” parameter in the ESME profile

Should the request fail any of the above verification parameters, thebind receiver request is rejected with a configurable SMPP error code.In alternate embodiments, a SNMP trap can be sent. Of course, where theESME bind receiver request is accepted, the ESME 70 is permitted toreceive SMPP messages from the invention 100.

The ESME Receiver Manager 110A monitors and maintains the SMPPconnection with the connected ESME(s). It is also responsible to provideESME Lookup Server 192 with the status of each ESME 70.

In alternate embodiments, the invention 100 can maintain and ensure thestatus of a SMPP receiver connection by sending enquire link messages inconfigurable time intervals to the connected ESME 70. The connected ESME70 is to respond with a enquire link response message, indicating theconnection is available. Incoming enquire links will be answered with anenquire link response message. If the connected ESME 70 does not respondto a enquire link message, the invention 100 sends a unbind message tothe connected ESME 70, and the connection is terminated. Practitionersskilled in the art will recognize that other protocols may be employedand managed accordingly without necessarily diluting the scope andintent herewith.

The logic of the invention 100 has been articulated to throttle outgoingSMPP receiver links in order to prevent excessive traffic from beingsent to external entities. In an ESME Receiver bind, only the numbers ofmessages defined by the throttling parameter (in messages/second orother such parameter) configured in the ESME Receiver profile areallowed. Subsequent messages are stored in the buffer (where configured)or rejected with a configurable logical error code.

The ESME Receiver Manager 110A supports multiple message handling andbuffering configurations. Illustratively, such configurations include,Non-Buffered Mode, Circular Buffered Mode and Fixed Buffered Mode. Forall buffering modes, Deliver_SM messages will be delivered to thedestination ESME 70 immediately if connection is available. TheDeliver_SM response received from the ESME 70 will be relayed back tothe originating SMSC 60A or the invention's 100 MSC Module 180. In caseswhere the ESME 70 does not respond within the configurable timeoutperiod, a Deliver_SM response with configurable error code (defaultESME_RDELIVERYFAILURE) will be returned. In continuing with theillustrative embodiments, in Non-Buffered Mode, if there is noconnection established to the destination ESME, messages will berejected immediately with configurable error code (defaultESME_RX_T_APPN). In Circular Buffered Mode, if there is no ESMEconnection or throttle exceeded, messages will be stored in the circularbuffer and positively acknowledged. When the buffer is full, the newmessage will overwrite the oldest one. When the connection isreestablished, the messages will be delivered from the bufferimmediately to the ESME 70. Before the buffer gets cleared, new incomingmessages will be stored in the buffer (and positively acknowledged).Once the buffer is cleared, new incoming messages will be delivered tothe ESME directly. In Fixed Buffered Mode, if there is no ESMEconnection or throttle exceeded, messages will be stored in the fixedsize buffer and positively acknowledged. When the buffer is full, thenew message will be rejected with configurable error code (defaultESME_RMSGQFUL). When the connection is re-established, the messages willbe delivered from the buffer immediately to the ESME 70. Before thebuffer gets cleared, new incoming messages will be stored in the buffer(and positively acknowledged if buffer is available). Once the buffer iscleared, new incoming messages will be delivered to the ESME 70directly.

The invention's 100 Reply-SMS Server 130 supports the generation ofresponse messages to confirm the originating subscribers that messageget delivered successfully. A Reply-SMS message will be generated onlywhere this feature has been articulated and enabled in the destinationESME profile and the message get successfully delivered to the ESME 70.Reply-SMS messages will be sent as SMPP Submit SM messages to theconnected SMSC(s) 60A via the SMSC Transmitter Manager 140. The greetingmessage to be sent is configurable on a per ESME 70 basis.

Continuing with reference to FIG. 1, the inventions' 100 SMSCTransmitter Manager 140 is responsible for SMPP transmitter connectionsto the SMSC(s) 60A and the invention's 100 MSC Module 180. The SMSCTransmitter Manager 140 provides Connection management functionality as,establishing connections, and connection monitoring. In establishingconnections, the invention's 100 SMSC Transmitter Manager 140 initiatesSMPP Transmitter connections to configured SMSC(s) 60A. An SMPPTransmitter link to an SMSC 60A must be established before messages canbe sent to it. The, the computer program product which implements thesystem and method for implementing a Universal Messaging Gateway (UMG)100 establishes all SMPP connections to SMSC(s) 60A upon startup.Configuration is also supported to disable this auto connection feature.In addition, in alternate embodiments, a GUI interface providescapabilities to disconnect and re-connect any SMPP connection. The SMSCTransmitter Manager 140 supports connections to multiple SMSCs 60A. Ifmultiple connections to the same SMSC account need to be established,multiple SMSC profiles with the same login parameters can be created. Inconnection monitoring, the SMSC Transmitter Manager 140 monitors andmaintains the SMPP connection with the connected SMSC(s) 60A. Inalternate embodiments, the, the computer program product whichimplements the system and method for implementing a Universal MessagingGateway (UMG) 100 can maintain and ensure the status of a SMPPtransmitter connection by sending enquire link messages to the connectedSMSC 60A. The connected SMSC 60A is to respond with a enquire linkresponse message, indicating the connection is available. Incomingenquire links will be answered with an enquire link response message. Ifthe connected SMSC 60A does not respond to a enquire link message, the,the computer program product which implements the system and method forimplementing a Universal Messaging Gateway (UMG) 100 sends a unbindmessage to the connected SMSC 60A, and the connection is terminated. Theinvention 100 will try to re-establish the connection if Auto Start isconfigured to True (or other such configurable parameter).

The invention's 100 ESME Lookup Server 192 provides a CORBA interfacefor ESME status lookup (although those skilled in the art will recognizethat there are a variety of protocols which serve similar technical andmechanical purposes and ends which may be employed without diluting theintent and scope of the invention of present). The invention's 100 HLRModule 190 sends requests to ESME Lookup Server to query the status ofthe ESME 70.

1. A middleware platform system comprising: at least one applicationservice provider; at least one message delivery element; a universalmessage gateway including a first common interface for connecting tosaid at least one application service provider and a second commoninterface for connecting to said at least one message delivery element;said universal message gateway further including a mobile switchingcenter module; said mobile switching center module configured to receivemessage service traffic from said at least one message delivery element;and said universal message gateway being configured to direct saidmessage service traffic to a virtual mobile station address associatedwith said at least one application service provider, wherein at leastone of said message delivery element sends network originatedtelecommunications messaging traffic to said universal message gateway.2. The system of claim 1, wherein the message delivery element is ashort message service center (SMSC).
 3. The system of claim 3,comprising a plurality of SMSCs wherein at least two of said SMSCs aredisparate in design.
 4. The system of claim 1 wherein the messagedelivery element is an multi-media message service center (MMSC).
 5. Thesystem of claim 1 comprising a plurality of MMSCs wherein at least twoof said MMSCs are disparate in design.
 6. The system of claim 1 whereinsaid universal message gateway further comprises an home locationregister module; said home location register module configured toreceive message service traffic from said at least one message deliveryelement.
 7. The system of claim 1, wherein said first common interfaceincludes a first receiver manager which interacts with said ESME, andsaid second common interface includes a second receiver manager whichinteracts with an SMSCs.
 8. The system of claim 1, wherein saidtelecommunications messaging traffic includes at least one ofMulti-Media traffic, interactive and/or synchronous mobile text, andshort message service traffic.
 9. The system of claim 1, wherein saidapplication service provider is associated with an ESME.
 10. The systemof claim 9, wherein said routing engine is configured to route saidtelecommunications messaging traffic to said at least one ESME within atleast one of parameter selected from the group consisting of SMSCConnection ill, Termination TON/NPI/MSISDN, Origination TON/NPI/MSISDN,protocol ID, data coding scheme, and SMSC address.
 11. The universalmessage gateway of claim 1, wherein said first common interface is basedon the short message peer to peer (SMPP) protocol.
 12. The universalmessage gateway of claim 1, wherein said universal message gateway isfurther configured to perform at least one of a throttling function, aqueuing function, and a buffering function.
 13. The universal messagegateway of claim 11, further comprising an SMS reply server configuredto generate a response message to confirm a successful delivery of amessage to said at least one ESME.